CVE-2026-40090
Zarf has a Path Traversal via Malicious Package Metadata.Name — Arbitrary File Write
Description
Zarf is an Airgap Native Packager Manager for Kubernetes. Versions 0.23.0 through 0.74.1 contain an arbitrary file write vulnerability in the zarf package inspect sbom and zarf package inspect documentation subcommands. These subcommands output file paths are constructed by joining a user-controlled output directory with the package's Metadata.Name field read directly from the untrusted package's zarf.yaml manifest. Although Metadata.Name is validated against a regex on package creation, an attacker can unarchive a package to modify the Metadata.Name field to contain path traversal sequences such as ../../etc/cron.d/malicious or absolute paths like /home/user/.ssh/authorized_keys, along with the corresponding files inside SBOMS.tar. This allows writing attacker-controlled content to arbitrary filesystem locations within the permissions of the user running the inspect command. This issue has been fixed in version 0.74.2.
INFO
Published Date :
April 15, 2026, 4:17 a.m.
Last Modified :
April 23, 2026, 5:16 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | MITRE-CVE | ||||
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update Zarf to version 0.74.2.
- Avoid untrusted package inputs.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-40090.
| URL | Resource |
|---|---|
| https://github.com/zarf-dev/zarf/pull/4793 | Issue Tracking Patch |
| https://github.com/zarf-dev/zarf/security/advisories/GHSA-pj97-4p9w-gx3q | Patch Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-40090 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-40090
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-40090 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-40090 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Apr. 23, 2026
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:a:lfprojects:zarf:*:*:*:*:*:*:*:* versions from (including) 0.23.0 up to (excluding) 0.74.2 Added Reference Type GitHub, Inc.: https://github.com/zarf-dev/zarf/pull/4793 Types: Issue Tracking, Patch Added Reference Type GitHub, Inc.: https://github.com/zarf-dev/zarf/security/advisories/GHSA-pj97-4p9w-gx3q Types: Patch, Vendor Advisory -
New CVE Received by [email protected]
Apr. 15, 2026
Action Type Old Value New Value Added Description Zarf is an Airgap Native Packager Manager for Kubernetes. Versions 0.23.0 through 0.74.1 contain an arbitrary file write vulnerability in the zarf package inspect sbom and zarf package inspect documentation subcommands. These subcommands output file paths are constructed by joining a user-controlled output directory with the package's Metadata.Name field read directly from the untrusted package's zarf.yaml manifest. Although Metadata.Name is validated against a regex on package creation, an attacker can unarchive a package to modify the Metadata.Name field to contain path traversal sequences such as ../../etc/cron.d/malicious or absolute paths like /home/user/.ssh/authorized_keys, along with the corresponding files inside SBOMS.tar. This allows writing attacker-controlled content to arbitrary filesystem locations within the permissions of the user running the inspect command. This issue has been fixed in version 0.74.2. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L Added CWE CWE-22 Added Reference https://github.com/zarf-dev/zarf/pull/4793 Added Reference https://github.com/zarf-dev/zarf/security/advisories/GHSA-pj97-4p9w-gx3q